Skip to content

Bump linux unittest runner to linux.2xlarge.memory #15400

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 1 commit into from
Oct 27, 2025
Merged

Bump linux unittest runner to linux.2xlarge.memory #15400

merged 1 commit into from
Oct 27, 2025

Conversation

@GregoryComer
Copy link
Member

@GregoryComer GregoryComer commented Oct 27, 2025 •
edited
Loading

Summary

Unittest jobs are dying since #15180. I'm not entirely sure why the jobs passed on the PR, but they are failing consistently since on trunk. Testing a runner size bump (2xlarge -> 2xlarge.memory) to see if that resolves it.

Example logs (from another PR). Note that the exit code (137 / SIGKILL) likely means OOM kill.

The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
...
Process completed with exit code 137.

@pytorch-bot
Copy link

pytorch-bot bot commented Oct 27, 2025 •
edited
Loading

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/15400

Note: Links to docs will display an error until the docs builds have been completed.

❌ 2 New Failures, 2 Pending

As of commit 2a25e87 with merge base cd6f2e2 (image):

NEW FAILURES - The following jobs have failed:

This comment was automatically generated by Dr. CI and updates every 15 minutes.

@meta-cla meta-cla bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Oct 27, 2025
@github-actions
Copy link

This PR needs a release notes: label

If your change should be included in the release notes (i.e. would users of this library care about this change?), please use a label starting with release notes:. This helps us keep track and include your important work in the next release notes.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "release notes: none"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.

@GregoryComer GregoryComer mentioned this pull request Oct 27, 2025
Merged
@GregoryComer
Copy link
Member Author

GregoryComer commented Oct 27, 2025 •
edited
Loading

Voxtral and samsung failures are due to running on a fork (I put up #15401 and #15402 to fix this).

@GregoryComer GregoryComer marked this pull request as ready for review October 27, 2025 22:19
@GregoryComer GregoryComer merged commit c0c3338 into pytorch:main Oct 27, 2025
143 of 146 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@SS-JIA SS-JIA SS-JIA approved these changes

Assignees

No one assigned

Labels

CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@GregoryComer @SS-JIA